V307 EXPERIMENTAL - REAL CHARACTERS DIRECTORY SWAP (NO EEex REQUIRED)
====================================================================
Base: V306. This is an experimental alternative to V306. It has NOT been
verified against the player's real Windows BaldurII.exe session. Keep V306
available separately until you have tested V307 successfully.

DESIGN: When a verified account login is received from the original BG2
account UI, the native folder router performs your proposed parent-folder
switch without recursively copying or deleting subfolders:

  1. Confirm that the requested account is the authenticated logged account.
  2. Rename Documents/Baldur's Gate II - Enhanced Edition/characters/ to an
     isolated group OUTSIDE characters/ on the SAME DRIVE (atomic rename).
  3. Create a new empty characters/ parent.
  4. MOVE EVERY existing subfolder back into the new parent. This includes
     characters/Kronas, characters/Drakhysys, all other accounts, and every
     unrelated subfolder. Original file contents remain in place.
  5. MOVE every non-character metadata file back as well.
  6. Old loose shared .CHR/.BIO files are kept outside BG2's Import view for
     manual review; they are NOT deleted and NOT automatically restored.
  7. Only the verified account's real CHR data is exposed in the clean parent
     as numbered native copies: characters/dra01.CHR or characters/kro01.CHR.
  8. Normal BG2 Import/Export and Done/Cancel screens are preserved; valid
     exports are verified and copied back to characters/<logged account>/.
  9. On logout, the router removes ONLY committed temporary native copies;
     all permanent account subfolders and characters remain unchanged.

CRITICAL DIFFERENCE FROM A LITERAL RECURSIVE COPY/DELETE:
The parent folder is actually renamed, but no account folders are recursively
copied, duplicated, deleted, or merged. This avoids the nesting/collision problem
in the original pseudocode. The same rule applies to all registered accounts.

SAFETY AND INTERRUPTIONS:
- No automatic character backup/restore mechanism. Old loose shared CHRs are
  preserved in _DRAKHYSYS_V307_UNASSIGNED_ROOT_ISOLATION/group_*/ for review.
- A transactional journal outside characters/ records any interrupted move.
- If installation/login reports an unfinished swap, CLOSE BG2 and STOP the
  router service; then run RECOVER_V307_FOLDER_SWITCH.bat to restore the
  PRE-SWAP original directory before trying again.
- Do not manually delete any group folder or JSON manifest before verifying
  that you have all desired account characters.
- If Windows locks the parent or any child directory during a move, the
  switch may fail safely and require the manual recovery helper.
- BG2 built-in/sample character entries may still appear in native Import;
  they do not necessarily originate from files under characters/.
- Only one account may use a single BG2 Documents profile at a time; this is
  NOT a system-wide security ACL and is not safe for simultaneous BG2
  instances sharing the same Documents/characters directory.

INSTALL / TEST:
1. Close BG2 completely. Keep a separate tested working build if needed.
2. Extract V307 somewhere outside the game folder; run
   SETUP_IN_GAME_ACCOUNTS.bat, selecting your real BG2 game and Documents paths.
3. Launch normal BaldurII.exe (no InfinityLoader). Log into Drakhysys.
4. Run CHECK_ACCOUNT_CHARACTER_ACCESS.bat and verify draXX.CHR are mounted.
5. Open native Import and Export and test. EXIT BG2 normally.
6. Log into Kronas. Verify no draXX.CHR are present in characters/ and test
   creating and exporting a Kronas character (should save to Kronas folder).
7. If any copy-back fails, do not manually delete the root .CHR files: they
   could be the only copy of a newly exported character.

A normal BG2 import panel is not a verified filesystem hook: temporary copies
remain mounted until logout. A perfectly isolated simultaneous multiplayer
profile would need separate user-data directories or a lower-level engine hook.
